home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000327_news@columbia.edu_Sat Sep 9 16:52:47 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA06993
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 9 Sep 1995 14:22:52 -0400
Received: by apakabar.cc.columbia.edu id AA26583
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 9 Sep 1995 14:22:51 -0400
Path: news.columbia.edu!panix!news.mathworks.com!news.duke.edu!agate!news.mindlink.net!van-bc!ddsw1!news.mcs.net!not-for-mail
From: les@MCS.COM (Leslie Mikesell)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kemir from a cron job
Date: 9 Sep 1995 11:52:47 -0500
Organization: /usr/lib/news/organi[sz]ation
Lines: 37
Message-Id: <42sgov$nen@Venus.mcs.com>
References: <DELqA9.I24@utnetw.utoledo.edu> <42qj0l$43o@apakabar.cc.columbia.edu>
Nntp-Posting-Host: venus.mcs.com
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <42qj0l$43o@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>In article <DELqA9.I24@utnetw.utoledo.edu>,
>craig szczublewski <crszczub@cse.utoledo.edu> wrote:
>>Is there anything special that would have to be specified from c-kermit
>>in order to run an upload (rather large) in the background (specifically
>>timed in the evening). I've tried running it in the background and it
>>crashes on me and fills up my /tmp filesystem with some junk file.
>>
>>anyone else ever tried this?
>>
>Lots of people, including me, do it all the time. Kermit does not write
>into /tmp unless you tell it to -- it's probably cron or something related
>to it.
Cron normally collects stdout and mails it to the owner of the cron
job, so the problem is likely kermit sending lots of stuff to
stdout.
>In general, the best method is to tell Kermit to read its commands from
>a file, and to redirect its standard output to some other file, for
>example (a cron job that runs every four hours):
>
> 0 0,4,8,12,16,20 * * * (cd /usr/olaf; kermit -y /oofa.scr > oofa.log)
>
>where oofa.scr is a file containing all the commands you want C-Kermit
>to execute.
I usually write a shell wrapper that will do some retries and report
complete failures, although you could do that in the kermit script
as well. Keep in mind that you don't ever want to go to 'connect'
mode in a script - do everything with 'input' and 'output', and
unless you are manually debugging, be sure 'take echo' and 'input echo'
are turned off.
Les Mikesell
les@mcs.com